From 03f4666994a72d72551cae31efb946aa742addca Mon Sep 17 00:00:00 2001 From: Matthias Clasen Date: Wed, 27 Jan 2016 23:22:02 -0500 Subject: [PATCH] composetable: Don't abort on unsupported escape sequences People might put all sorts of gunk in their .XCompose file, in the hope that XLib makes sense of it. Even if we don't make sense of it, we shouldn't abort, but instead ignore the lines we can't understand. Pointed out in https://bugzilla.redhat.com/show_bug.cgi?id=1301254 --- gtk/gtkcomposetable.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/gtk/gtkcomposetable.c b/gtk/gtkcomposetable.c index eaff054590..9b4cb15ef1 100644 --- a/gtk/gtkcomposetable.c +++ b/gtk/gtkcomposetable.c @@ -104,7 +104,9 @@ parse_compose_value (GtkComposeData *compose_data, uch = g_ascii_strtoll(words[1] + 1, NULL, 8); /* If we need to handle other escape sequences. */ else if (uch != '\\') - g_assert_not_reached (); + { + g_warning ("Invalid escape sequence: %s: %s", val, line); + } } if (g_utf8_get_char (g_utf8_next_char (words[1])) > 0) -- 2.30.2